home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950929-19951130
/
000248_news@columbia.edu_Sun Oct 29 20:23:46 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA00173
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 30 Oct 1995 18:18:11 -0500
Received: by apakabar.cc.columbia.edu id AA26496
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 30 Oct 1995 18:18:10 -0500
Path: news.columbia.edu!panix!news.cloud9.net!news.sprintlink.net!europa.chnt.gtegsc.com!usenet.eel.ufl.edu!afn10375
From: afn10375@afn.org (David A. Johns)
Newsgroups: comp.protocols.kermit.misc
Subject: Kermit freezes when inactive
Date: 29 Oct 1995 20:23:46 GMT
Lines: 26
Message-Id: <470nsi$c7e@huron.eel.ufl.edu>
Nntp-Posting-Host: freenet4.afn.org
X-Newsreader: TIN [version 1.2 PL2]
Apparently-To: kermit.misc@watsun.cc.columbia.edu
Has anyone seen anything like this?
I'm operating MS-Kermit 3.14 over a network running TCP/IP. It
communicates through an ethernet card with a packet driver and
winpkt.com. Sometimes I call it up from DOS and sometimes in a DOS
window under Windows 3.1.
Fairly regularly if I'm logged into a remote host, if I let the
connection sit idle for a while, when I try to use it, it's frozen.
Kermit itself is not frozen, since I can escape to the command line and
even use other sessions. If I give the hangup command, however, the
cursor will move back to the beginning of the command line and Kermit will
lock up solid. If I'm in DOS, I have to reboot. If I'm in Windows, I
can ctrl-alt-del back to Program Manager, but no program will be able to
access the network until I reboot the computer (if I restart Kermit, it
will not connect, and Trumpet winsock will not start up).
I also use MSKermit to connect to these same hosts from home over a phone
line, and this lockup never happens. It is not being caused by an
inactivity time-out at the other end. It only happens with MSKermit; I
also use various winsock-based telnet clients, and have never had this
happen.
Does anyone have a clue? I don't, and I'd sure appreciate one.
David Johns